The content of this section:
Traefik Introduction
Two services deployed for testing
Role Based Access Control configuration (Kubernetes 1.6+ only)
Deploying Traefik
Deploying Ingress
Deploying the Traefik UI
Access test
Health Check
I. Introduction of TraefikTraefik is a front-
Kubernetes 1.9 clusters use traefik to publish services
This section describes how to use traefik to publish services in the kubernetes 1.5.2 cluster environment. Traefik is deployed in the daemonset mode. The http protocol is used to connect to the api-server, and rbac is n
1. Reference documentationhttp://traefik.cn/2. Simple way to accessReference documentshttps://tonybai.com/2018/06/25/the-kubernetes-ingress-practice-for-https-service/Previous: Traefik Basic deployment record, describes the simplest HTTP access Traefik, the access process reference is shown below:Client---(via HTTP)---> Traef
[TOC]DescriptionThere is no detailed explanation of the Kubernetes's service exposure and Traefik's principles. The Traefik principle can be consulted in the official documentation: https://docs.traefik.io/, This document can also be consulted about the service exposure of kubernetes and the rationale for using Traefik as a k
1. Reference documentationhttp://traefik.cn/2. Simple way to accessReference documentshttps://tonybai.com/2018/06/25/the-kubernetes-ingress-practice-for-https-service/Previous: Traefik Basic deployment record, describes the simplest HTTP access Traefik, the access process reference is shown below:Client---(via HTTP)---> Traef
1. Reference documentationhttp://traefik.cn/2. Simple way to accessReference documentshttps://tonybai.com/2018/06/25/the-kubernetes-ingress-practice-for-https-service/Previous: Traefik Basic deployment record, describes the simplest HTTP access Traefik, the access process reference is shown below:Client---(via HTTP)---> Traef
The previous article describes the use of Traefik for service publishing in Kubernetes 1.5.2 cluster environments. Traefik is deployed in Daemonset mode, and the connection Api-server is the HTTP protocol, and RBAC is not configured. This article describes the deployment of Traefik for service publishing in the K8s 1.9
Use traefik to publish a service in a kuberneters Cluster
The previous article has introduced the implementation principle and configuration of k8s ingress. This article will introduce the alternative solution traefik. Before starting the configuration, let's review the implementation scheme of the k8s Service released by ingress. The ingress solution requires the following components:
1. Reverse Proxy Serv
The implementation principle and configuration of k8s Ingress are described in the previous article, and the alternative Traefik is described in this paper. Before we start the configuration, let's review the implementation of the Ingress release k8s service, which requires the following components to be used ingress scenarios:1. Reverse Proxy Load Balancer2. Ingress control3, IngressWhere Ingress control is responsible for communicating with apiserve
In the previous article we briefly introduced the next Traefik and how HTTP access, but in the actual production environment is not just HTTP forwarding access, there is HTTPS forwarding access,Previous: Traefik Basic deployment record, describes the simplest HTTP access Traefik, the access process reference is shown below:Client---(via HTTP)--->
Ingress+haproxy this way of implementing service load balancing, ingress controller polls the pods state behind the service, rebuilds the Haproxy configuration file, and then restarts Haproxy, So as to achieve the purpose of service discovery. This principle is not for haproxy service will be temporarily interrupted. Is there a good alternative? Previously saw Golang implementation of the Træfik, can seamlessly docking kubernetes, and do not need ing
How does one use nginx to solve the cross-origin problem of basic auth in k8s traefik ?, Nginxk8sPurpose
Currently, k8s ingress is used in combination with traefik. At this time, you need to add a basic auth Security Authentication for a domain name. The original traefik can also be configured normally (many production environments already use
The content of this section:
Service Discovery and load balancing
Ingress Combat
First, service discovery and load balancingIn the previous installation deployment Kubernetes cluster, it was simple to demonstrate that pod and Service,kubernetes implemented service discovery and load balancing for containers within the Kubernetes cluster through
The Kubernetes network model is made up of four parts from inside to outside:
The network where the pod interior container resides
The network where the pod resides
Network for communication between pod and service
Network of communication between outside and service
It is recommended that you understand the network model of Docker before reading this article. Refer to the author's first two articles [
What is 1.1 kubernetes?First, it is a new, container-based, distributed architecture leading solution. is an open source version of Google's Borg (large-scale cluster management system).Second, if the system design follows the Kubernetes design idea, then the traditional system architecture and business does not have much to do with the underlying code or function modules (such as load balancing, service se
Guide:Kubernetes a ride on the dust to open, then the enterprise should start to kubernetes migration? Under what circumstances do you really accept it? Some of the technology frontier companies first-step practice is probably the most persuasive and reference value. This article is a good reference.1Kubernetes now rage, it is part of a massive cloud-native movement. All major cloud providers use it as a solution for deploying cloud-native application
Description: Use the Grafana official plugins (Grafana-kuberneres-app) Link Prometheus show kubernetes informationNote: All monitoring-related information is placed on the Namespace=monitorGithub:https://github.com/grafana/kubernetes-app1, Installation PrometheusProm-rbac.yamlapiVersion: rbac.authorization.k8s.io/v1beta1kind: ClusterRolemetadata: name: prometheus namespace: monitorrules:- apiGroups: [""]
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.